Data Backup 2.0.6

Thank you for using Prosoft Engineering's Data Backup 2.0.

Please refer to the manual for instructions on how to run Data Backup 2.0.

Data Backup 2.0.5 supports OS X 10.4, OS X 10.3 and OS X 10.2.

Uninstalling Data Backup 2.0
Use the Data Backup Uninstaller app in the Data Backup 2.0 folder to uninstall the application.  You will need an administrator password.

Technical information
Data Backup 2.0 is split into two executables, the background “Executor” task and the Data Backup UI.  All scheduling, backup and restore operations are carried out in the “Executor” class.  After installation, the Executor task is started at boot time by /Library/StartupItems/Executor/Executor.

Please note, on backup destination volumes, Data Backup 2.0 stores internal information and old versions in the hidden directory “.indelible-info”.

Changes in Data Backup 2.0.6
Fixed hang on GUI launch when DiskArbitration framework does not deliver all events (this shows as a hang at "Initializing" or "Connecting to Executor")
Fixed problem where selecting "View->Log Files" using OS X 10.2 would crash GUI
Fixed problem where minimize button on main window disappeared after running a backup on OS X 10.3

Changes in Data Backup 2.0.5
Mac OS X 10.4 ("Tiger") compatibility
Automatically checks for updates (selectable)
Better handling for symbolic links
Locked file attributes are propagated to the backup copy
Improved automatic mounting on Appleshare volumes
Turned off warning messages for system temporary files (Unix pipes)
Better compatibilty with Thursby DAVE

Changes in Data Backup 2.0.4
Admin password is no longer required every time program is launched (turn off Preferences->General->Retain authorization to require the password everytime)
Schedule will now show name of operations sets scheduled (for new schedules created with 2.0.4)
Added "Create New Folders" and "Missing Items" disposition option (Leave, Delete, Move To Trash).  Please see the manual for more details.
Improved support for AppleShare and other remote volumes.  Now handles permissions properly and can also automatically mount volumes for scheduled backups.
Added Preferences for:
	Logging
	Time display
	Automatic removal of old versions
Added success/fail messages when backup/synchronization/restore completes
Added minutes and hours as options for Interval schedules
"Verbose" log files are now turned off by default.

Changes in Data Backup 2.0.3
Fixed volume confusion problem for multiple external drives
Fixed scheduling problem with multiple dates
Now correctly sets creation times on HFS files
Fixed "can't update" issue with non-HFS volumes
Fixed Schedule List screen update after scheduled item removal
Fixed typos
Added warning message for versioned/synchronize to non-empty folder
Faster launch time

Changes in Data Backup 2.0.2
Now sets a "Default Destination" for quick backup types
Better handling for communication errors

Changes in Data Backup 2.0.1
Fixed issue #101 - Incremental backups fail after restart on OS X 10.3.3
Fixed issue #102 - Deleting source files during backup causes complete backup to fail
Fixed issue #103 - Incremental backups keep copying same files
Fixed issue #104 - Rule to exclude Non-Document files reads as excluding "Document files"
Fixed issue #106 - Day of week/interval schedules not functioning

Known issues:
Restores of small numbers of files may take a long time if the destination being restored from has a large number of files.

Encryption is only supported to/from HFS volumes

Files over 4GB in size cannot be encrypted or compressed

Incremental backups from file systems which do not support the backup time attribute (Windows File Sharing, NFS, UFS) may miss files which have been copied or moved within the directory tree.  Doing "Full" backups on a regular basis will ensure that all files are backed up.

Synchronizations with file systems which do not support the backup time attribute (Windows File Sharing, NFS, UFS) may not propagate deletions properly.

Submitting bug reports

Submit bugs via e-mail to support@prosofteng.com

When submitting bugs, please attach your preference file and the appropriate log files.  If a backup or restore operation fails, please attach the appropriate “.execlog” file (.execlog files are named by the time at which the backup/restore was begun) and the “executor.log” file.  If you encounter an issue with the UI, please attach the "databackup.log" file.  When in doubt, attach as many log files as you can find. Log and preference files are stored in the following directories:

/Library/Logs/databackup
/Library/Preferences/com.prosofteng.databackup

Also, please attach any relevant "crash logs" that may have been saved:
/Library/Logs/CrashReporter/DataBackup.crash.log and /Users/<User Name>/Library/Logs/CrashReporter/DataBackup.crash.log
/Library/Logs/CrashReport/Executor.crash.log